ci: skip most CI checks if title contains citest skip [citest_skip]#585
Merged
ci: skip most CI checks if title contains citest skip [citest_skip]#585
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideAdds a conditional to most GitHub Actions CI jobs so they are skipped when a pull request title contains the marker string "[citest_skip]". Sequence diagram for conditional CI job execution based on PR title markersequenceDiagram
actor Developer
participant GitHub
participant WorkflowDispatcher
participant Job_ansible_lint
participant Job_codespell
participant Job_markdownlint
Developer->>GitHub: Open pull_request with title containing [citest_skip]
GitHub-->>WorkflowDispatcher: pull_request event
WorkflowDispatcher->>Job_ansible_lint: Evaluate if !contains(title, [citest_skip])
alt Title_contains_citest_skip
Job_ansible_lint-->>WorkflowDispatcher: Condition false
WorkflowDispatcher-->>Job_ansible_lint: Skip job
else Title_does_not_contain_citest_skip
Job_ansible_lint-->>WorkflowDispatcher: Condition true
WorkflowDispatcher-->>Job_ansible_lint: Run job steps
end
WorkflowDispatcher->>Job_codespell: Evaluate if !contains(title, [citest_skip])
alt Title_contains_citest_skip
Job_codespell-->>WorkflowDispatcher: Condition false
WorkflowDispatcher-->>Job_codespell: Skip job
else Title_does_not_contain_citest_skip
Job_codespell-->>WorkflowDispatcher: Condition true
WorkflowDispatcher-->>Job_codespell: Run job steps
end
WorkflowDispatcher->>Job_markdownlint: Evaluate if !contains(title, [citest_skip])
alt Title_contains_citest_skip
Job_markdownlint-->>WorkflowDispatcher: Condition false
WorkflowDispatcher-->>Job_markdownlint: Skip job
else Title_does_not_contain_citest_skip
Job_markdownlint-->>WorkflowDispatcher: Condition true
WorkflowDispatcher-->>Job_markdownlint: Run job steps
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- Several workflows (e.g., codeql with a
scheduletrigger, or any triggered onpush) now referencegithub.event.pull_request.title, which is not defined for non-pull_requestevents; consider guarding the condition withgithub.event_name != 'pull_request' || !contains(github.event.pull_request.title, '[citest_skip]')to avoid runtime errors and unintended skips. - If the intention is to skip all CI for these PRs, you may want to put the
ifcondition at the workflow or a common job level (or via a shared reusable workflow) to avoid duplicating the[citest_skip]logic across many jobs and keep future changes to the skip behavior in one place.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Several workflows (e.g., codeql with a `schedule` trigger, or any triggered on `push`) now reference `github.event.pull_request.title`, which is not defined for non-`pull_request` events; consider guarding the condition with `github.event_name != 'pull_request' || !contains(github.event.pull_request.title, '[citest_skip]')` to avoid runtime errors and unintended skips.
- If the intention is to skip all CI for these PRs, you may want to put the `if` condition at the workflow or a common job level (or via a shared reusable workflow) to avoid duplicating the `[citest_skip]` logic across many jobs and keep future changes to the skip behavior in one place.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
When we submit a PR for a CI update or docs, we do not want to start CI checking for ansible-lint, qemu, etc. When we are doing CI updates to 30 or more roles, this fires off a lot of unnecessary tests, which sometimes causes the linux-system-roles org in github to be throttled. When submitting a PR that can skip ci, use "[citest_skip]" in the PR title. Signed-off-by: Rich Megginson <[email protected]>
When we submit a PR for a CI update or docs, we do not want to start CI checking for ansible-lint, qemu, etc. When we are doing CI updates to 30 or more roles, this fires off a lot of unnecessary tests, which sometimes causes the linux-system-roles org in github to be throttled. When submitting a PR that can skip ci, use "[citest_skip]" in the PR title. Signed-off-by: Rich Megginson <[email protected]>
vojtechtrefny
approved these changes
Feb 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When we submit a PR for a CI update or docs, we do not want to start CI checking
for ansible-lint, qemu, etc. When we are doing CI updates to 30 or more
roles, this fires off a lot of unnecessary tests, which sometimes causes the
linux-system-roles org in github to be throttled.
When submitting a PR that can skip ci, use "[citest_skip]" in the PR title.